Fixing Corrupt Indexes with Net Change

Kourier Integrator Online Help

Fixing Net Change Write Errors

In rare circumstances you may encounter Kourier Error KMK-153, which indicates there is a problem writing to the Kourier Net Changes files. You may have received an Event Notification email or seen this error in the Kourier Event log. The message will look something like this:

Export <export name> failed. The Kourier net change file for <file name> has been corrupted because a write to the net change file failed on 01 OCT 2013 at 23:41:21. Contact your system administrator to determine the cause of this fatal condition. See record KCL.UPDATELOG_ERRORS in file &PH& for additional details.

The procedure for fixing this is described below.

Example of Kourier Net Change write error log item

>ED &PH& KCL.UPDATELOG_ERRORS

0001: /home/Account/KT_CHGLOG/<file name>

0002: 16711

0003: 85281

0004: 362641:4

0005: 40019

0006: atsumich

0007: 3401

Where:

0001 – is the full path to the change log file that could not be written

0002 – is the date (in internal format) of the last time a record could not be written to the file

0003 – is the time (in internal format) of the last time a record could not be written to the file

0004 – is the item-id (key) that could not be written to the file

0005 – is the status code returned by UniVerse (see SYS.MESSAGE file in the UV account for the text of the status code)

0006 – is the @LOGNAME of the user that attempted the write

0007 – is the @USERNO of the user that attempted the write

If the status code in Attribute 5 is less than 6 digits, you must add leading zeroes so you have a 6-digit key before trying to edit the SYS.MESSAGE file. For example, to edit the item in as shown in the example above you would need to use 040019 as the item-id.

How to Correct the Issue

In order to correct this issue you must perform the following steps:

Delete the item KCL.UPDATELOG_ERRORS from the &PH& file. This will stop the KMK-153 alert.
If the KCL_INDEX is missing from the source file, you must run KT.SETUPNETCHG to re-create the index.
If you are using the Related Data Files Guide features in your exports then the best approach is to use the KCL.SETLOG command to:
- Cause all records in the affected file to be processed in Net Change:
  - Example: KCL.SETLOG <file name>
- If you can select a subset of records by date, you could just force those records in Net Change:
  - Example: KCL.SETLOG <file name> WITH <date> "9/30/2013"
If you are not using the Related Files feature then you must do a full refresh of all exports for the file indicated.

If you have any questions or need any assistance with this procedure, please contact Kore Technologies.